This is a demonstration of using the Visual Basic 5 AddressOf operator
to intercept Windows Messages. In particular, the WM_GETMINMAXINFO message 
which allows you to limit the size of a window when the user tries to 
drag its corners.

Currently, the only way to control the size of a form in VB is to place 
code in the Form_Resize event. This works, but is ugly. At the very least, 
the user can see the "rubberband" stretch as far as they want only to 
see it snap back again when Form_Resize fires. However, if MS Plus! is 
installed on the users machine or the user has used some other utility 
to display window contents while dragging, the effect is a flickering 
window as the window is forced to size to the users liking then snap 
back when the Form_Resize fires.

This method simple controls that "rubberband" to your specification so 
the window simply stops stretching once it reaches your defined limit.

!!CAUTION!!
VB5 has the capability to intercept any windows message with the drawback 
that doing so renders VB's debugging features effectively useless. If 
VB enters break mode due to an error in your code, it will crash because 
the procedure you defined to handle windows messages is frozen while windows 
is still sending it messages.
SAVE YOUR WORK EVERY TIME YOU RUN YOUR PROGRAM!
One way to keep VB from crashing is to compile your program into an executable 
and test it outside the VB environment.  This REDUCES the likelyhood of crashing 
VB or Windows itself.  Message handling should only be done if you need 
access to a message VB doesn't handle explicitly. ie, no need to handle 
the WM_SIZE message because it merely triggers VB's Form_Resize event.